Remote Account
The Remote account tab lets you make remote account settings.
Figure. Remote account level management: Remote account tab.
Field |
Description |
---|---|
Active |
Check this box to make this remote account active. |
Name |
A unique name for the account within this domain. |
Server |
Specify here the host name of the server that this remote account should collect messages from. Example:
Note: In the case POP3/IMAP run on non-standard ports, you can specify them: Note:
By default, only messages from INBOX of the remote server are downloaded, but you can override this. Use the following syntax: |
Server type |
Specify the protocol that should be used to collect messages:
Note:
The local account (specified in the Forward to: field, see below) must be an IMAP4 account. Note: If you do not mark to Leave messages on server (the Options tab), even in the case you choose IMAP, all emails will be deleted from the source folder. |
Username |
You need to specify the Username that is used to access the remote server to collect mail. |
Password |
The password for the Username specified above. |
Log in using APOP |
For extra security, and if the remote server supports it, you can specify that APOP is used for the login process. APOP is a secure login method using md5 encryption. |
TLS/SSL |
Specifies whether to use a TLS/SSL connection to access the remote account. We recommend leaving this option as the default (Detect TLS/SSL). Detect TLS/SSL The remote connection will be checked using the CAPA command for TLS support. If supported, the connection will continue in TLS/SSL mode. Direct TLS/SSL The connection will be made using TLS/SSL. Disable TLS/SSL No TLS/SSL will be used a non-secured TCP/IP connection will be established. |
Forward to |
An account should be specified here where messages will be forwarded if the local recipient cannot be found. In the case you use DOMAIN POP, the email address specified here receives emails where IceWarp Server cannot discern to whom to send mails fetched via a remote account to. Note: If you specify a path to a mailbox here, the folder structure of the remote server is created within this mailbox and no filters or Antispam processing is applied. Warning: You should also be aware that original receive times are only kept for IMAP collection as POP3 does not provide this information. Note: Even with IMAP accounts, if you specify a local email address in this field, IceWarp Server fetches only emails in Inbox. However, you can specify the path to a user's mailbox (e.g. icewarpdemo.com/joe). In this case, the folder structure of the account on the remote server (including emails in subfolders from a source IMAP server) is created within this mailbox, as well as no filters or Antispam processing are applied. |
Schedule |
Use the Schedule button to open the standard Schedule dialog where you can define a schedule for mail collection. Note: You can also set a global schedule (within a remote account template), allowing you to use this schedule rather than defining one for each remote account. Note: Choosing the Every x minutes option for email download and setting it to a short interval (say 5 or 10 minutes) can cause download overlaps. Note: If this situation occurs, you can resolve it by enabling POP3 locking on the remote server (provided that it is also IceWarp Server): |
Connect Now |
Use this button to connect to the remote server and collect mail immediately. |
Note: You may want/need to reset a downloaded emails index for a specific user. In the <install_dir>/config/<domain> directory, find the remote.<user_name>.<alphanumeric_string> file and delete it.